-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add supports for multiple security schemes in http server #1070
Conversation
Note that this means that the server is able to expose Things with different security requirements. For example, it is possibile to now have a Thing with `nosec` security scheme and one with `basic` security scheme. As a side effect, the OAuth example now works as explained in eclipse-thingweb#873. Fix eclipse-thingweb#204 eclipse-thingweb#873
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1070 +/- ##
==========================================
- Coverage 75.33% 75.16% -0.17%
==========================================
Files 80 80
Lines 15452 15577 +125
Branches 1477 1495 +18
==========================================
+ Hits 11641 11709 +68
- Misses 3775 3832 +57
Partials 36 36
☔ View full report in Codecov by Sentry. |
Thanks for your work @relu91 👍 No real review yet, just a note...
|
Yes, I forgot to mention that important note. It sort of needed if we wanted to fix #873. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have some very minor questions/proposal... I can live with the current state also.
I just have one question/concern. Since we want to publish a release soon. Do you think we will see issues/regressions? I mean.. a lot has been changed and moved around... If you feel comfortable I am OK as well 👍
About this point, I was worried too. What I know is:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the PR is fine. I added some minor comments..
We just need to decide whether we want to merge it before or after the upcoming release
Some notes:
|
Didn't know about this, I thought the tendency was to favor |
This PR improves the exposing process of the
http-server
. In particular, it focuses on the ability to handle multiple security schemes perhttp-server
instance. For example, now thehttp-server
can be configure to be able to hosts Things without security and Things with basic schemes:Note that this does not mean that now we can use multiple security schemes in the
security
field or thecombo
SecurityScheme`. For multiple security schemas, I think we can avoid implementing that feature, mainly because it is already deprecated in TD 1.1. On the other hand, the combo scheme will require some additional work. Moreover, this does not introduce support for form-level security fields. It is quite tricky to achieve and we need first to support form templating in the expose method properly.